Sidari Agbhan
Gallente
Unknown Soldiers
Systematic-Chaos
   |
Posted - 2009.12.08 04:23:00 -
[1]
I feel like I'm a bit late to the party on this one, but here goes. I'm not sure if anyone else has found this workaround, but I've been experimenting in isolation on my MacBook Pro for the last few days (wish I'd found this thread earlier) and have found a way to preserve most if not all of my settings (overview settings, tutorial preferences, menu displays, etc.) simply by replacing two files.
For me, the two crash-inducing files were in the EVE settings folder, which is in the same parent directory as the cache folder. After much trial and error (i.e. - backing up and renaming files in the settings folder and testing to see if the game worked when they recreated themselves), I was able to isolate the files "core_public__.dat" and "core_user_689624.dat" as the culprits behind the two stages of the crash that I experienced.
(NOTE: I saw on one post that it is not recommended that you mess around in the EVE settings folder, so please be advised that if you do so it is at your own risk)
Stage 1 workaround - getting the EVE client to load past the mini "splash" screen and into the main logon screen: When I renamed the file "core_public__.dat" and replaced it with a fresh version (which you can get by backing up and rename the settings folder), I found that I was able to get to the main EVE (Dominion) logon screen. I did have to repeat this step again when my client crashed after 30+ minutes of playtime, but it worked just as well.
Stage 2 workaround - getting the EVE client to load the character selection screen: After more trial and error, I was able to discover that when I replaced the file "core_user_689624.dat" with a fresh copy, the client was now able to transition from the login screen to the character selection screen (previously it was getting stuck after I entered my logon credentials and hit "log in"). I had to repeat this step again after the crash following my initial client fix, but it also worked the second time around.
Would be interested to see if this fix works for anyone else. Hopefully it will be a moot point tomorrow when the patch comes out, but until then this might be worth a try for you.
Cheers.
-SiD |